Amazon Web Services Elastic Load Balancing (via Codeless Connector Framework)

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Connectors Index


Attribute Value
Connector ID AWSELBConnector
Publisher Amazon Web Services
Used in Solutions AWS ELB
Collection Method CCF
Connector Definition Files AWSELBConnector_ConnectorDefinition.json
DCR Definition Files AWSELBConnector_DCR.json
CCF Configuration AWSELBConnector_PollingConfig.json
CCF Capabilities AmazonWebServicesS3
Microsoft Learn View on Learn

The AWS Elastic Load Balancing (ELB) connector for Microsoft Sentinel allows you to ingest access logs and flow logs from AWS Application Load Balancers (ALB), Network Load Balancers (NLB), and Gateway Load Balancers (GLB) into Microsoft Sentinel. These logs provide detailed information about requests processed by your load balancers and VPC traffic flows, enabling security monitoring, threat detection, and traffic analysis.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
AWSALBAccessLogs ?
AWSALBAccessLogs_CL ? ?
AWSELBFlowLogs ?
AWSELBFlowLogs_CL ? ?
AWSNLBAccessLogs ?
AWSNLBAccessLogs_CL ? ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

1. AWS CloudFormation Deployment

To configure access on AWS, use CloudFormation templates to set up the environment to send logs from ALB, NLB and GLB to your Log Analytics Workspace.

Deployment steps:

  1. Go to the Cloud Formation Templates, download the JSON template files.
  2. Go to AWS CloudFormation Stacks.
  3. First deploy the OIDCWebIdProvider.json template (skip if you already have an OIDC provider for Microsoft Sentinel).
  4. Then deploy the AWSS3ELB.json template with your parameters.
  5. Note down the following values from the stack outputs:
    • IAMRoleArn
    • ALBSQSQueueURL
    • NLBSQSQueueURL
    • NLBFlowLogsSQSQueueURL
    • GLBFlowLogsSQSQueueURL

Post-deployment Configuration:

Once the CloudFormation stack is successfully deployed:

Sending Logs:

After folder creation, configure your AWS services to send logs to the appropriate folders:

These logs will be ingested into the corresponding tables in your Log Analytics Workspace.

Table Mapping:

Note: In the AWSELBFlowLogsData table, a column named LogType will indicate whether a row is from NLB flow logs or GLB flow logs.

2. Connect new collectors

To enable the connector, click Add new collector, enter the required details, and click Connect. Connector Management Interface

This section is an interactive interface in the Microsoft Sentinel portal that allows you to manage your data collectors.

📊 View Existing Collectors: A management table displays all currently configured data collectors with the following information:

Add New Collector: Click the "Add new collector" button to configure a new data collector (see configuration form below).

🔧 Manage Collectors: Use the actions menu to delete or modify existing collectors.

💡 Portal-Only Feature: This configuration interface is only available when viewing the connector in the Microsoft Sentinel portal. You cannot configure data collectors through this static documentation.

Add new collector

AWS S3 connector

When you click the "Add new collector" button in the portal, a configuration form will open. You'll need to provide:

Account details

💡 Portal-Only Feature: This configuration form is only available in the Microsoft Sentinel portal.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Connectors Index